fix: prefer compatible advertised model routes - #148
Merged
Merged
Conversation
Contributor
|
🎉 This PR is included in version 0.10.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a model advertises both Chat Completions and Responses, prefer Chat Completions. The exact saved OpenCode V2.0.18 session error was a
response.output_item.addedevent whosefunction_callitem lacked the requiredargumentsstring while DeepSeek V4.1 Flash#maxwas calling the shell tool. The earlier annotation-event description was incorrect.This shared route policy applies by advertised endpoints, not by a DeepSeek model ID. In the current 84-model catalog, 66 entries advertise Chat and Responses, 10 advertise Messages only, and 8 advertise Chat only; no entry is Responses-only. Other models' Responses tool-call streams were not individually validated.
Validation after release:
file://config and completed the same model/variant shell-tool flow (TOOL_CALL_SMOKE_OK).